--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
docs/nomadmesh_pages.md v4.7.2-rc.6 (36474762) Text, 3.47 KB
NomadNet Network browser and Mesh Server pages
MeshChatX can serve pages from a Mesh Server (local Reticulum page node) found in the tools section and display them in the NomadNet browser. Pages are fetched over the usual Nomad path convention: T383838/page/<filename>.
Supported filenames
┌───────────┬──────────────────────────────────────────────────────────┐
│ Extension │ Role │
├───────────┼──────────────────────────────────────────────────────────┤
│ T383838.mu │ Micron markup (NomadNet default). │
│ T383838.md │ Markdown (GitHub-flavored features via the renderer). │
│ T383838.txt │ Plain text (shown escaped, monospace-friendly wrapping). │
│ T383838.html │ Static HTML with CSS only (see security below). │
└───────────┴──────────────────────────────────────────────────────────┘
If you add a page without a recognised extension, the server stores it as T383838.mu. Filenames with other extensions (for example T383838.exe) are rejected when saving through the API.
Plain text (T383838.txt)
Content is HTML-escaped and shown with pre-wrapped whitespace. There is no Markdown parsing on T383838.txt pages.
Markdown (T383838.md)
• Not the same engine as chat: Conversations use the lightweight T383838MarkdownRenderer (HTML-escaped first, then patterns for headers, bold, code, links). Nomad T383838.md pages use T383838marked (GFM-oriented) plus sanitisation, so features and edge cases can differ. Automated tests cover both paths.
• Use ATX headings with a hash and a space before the title, for example T383838# Title, T383838## Section, T383838#### Subsection. CommonMark requires that space; MeshChatX may normalise some common shorthand forms, but relying on the standard form is safest.
• Line breaks and spacing: the viewer preserves wrapping behaviour suitable for technical text; fenced code blocks keep indentation.
• Links are sanitised: off-mesh T383838http/T383838https links in rendered content are removed or restricted so the preview cannot drive external navigation without mesh-style URLs.
HTML (T383838.html)
• JavaScript is not executed: T383838script tags and event-handler attributes are stripped.
• External resources are blocked where possible: T383838@import and T383838url(...) pointing at T383838http://, T383838https://, or protocol-relative URLs are removed from CSS. Embedded T383838<style> blocks are kept; rules that target T383838html or T383838body are rewritten to apply to the viewer’s root container so your layout still applies.
• Links: T383838href values that are not mesh-style (T383838: paths, 32-character hex prefixes, T383838/page/..., T383838/file/..., or T383838# fragments) are removed. Images only keep T383838data:image/... sources for inline images.
• The viewer uses a sans-serif font for HTML and Markdown so pages do not inherit the monospace Micron chrome. You can override colours and typography with your own CSS.
Mesh Server API
• T383838POST /api/v1/page-nodes/{node_id}/pages with T383838name and T383838content saves a page; invalid extensions return 400 with a short message.
• Listed pages only include files with allowed extensions in the T383838pages/ directory.
Archives
Snapshots in Archives use the same rendering pipeline as the Nomad browser (Micron, Markdown, text, sanitised HTML) using the archived T383838page_path to pick the format. Exports keep the original extension when it is T383838.mu, T383838.md, T383838.txt, or T383838.html.
See also
• Architecture overview: T383838meshchatx.md in this docs bundle.
• Default Nomad entry path remains T383838/page/index.mu unless you change the URL in the browser.
──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────